Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: f8a10da0ea675b648a1479ebfa9890f8180cbdd351dd71d73a7390f45c186b01

Tx prefix hash: c33a7ffbe3ff6b64d9f0674d8d8d149af123e7286cf53ba5b87706b4bd7d2ee3
Tx public key: 36e0dee4d896fc929a228f61226af0d4abdab25e22972a354bc3378a6b716a4d
Timestamp: 1717984296 Timestamp [UCT]: 2024-06-10 01:51:36 Age [y:d:h:m:s]: 00:279:07:41:57
Block: 1040851 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199619 RingCT/type: yes/0
Extra: 0136e0dee4d896fc929a228f61226af0d4abdab25e22972a354bc3378a6b716a4d0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5179cdf8fffc906332dc413d4572795c53ba49b6ceddd09f4b315a667d94644 0.600000000000 1509514 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1040861, "vin": [ { "gen": { "height": 1040851 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5179cdf8fffc906332dc413d4572795c53ba49b6ceddd09f4b315a667d94644" } } ], "extra": [ 1, 54, 224, 222, 228, 216, 150, 252, 146, 154, 34, 143, 97, 34, 106, 240, 212, 171, 218, 178, 94, 34, 151, 42, 53, 75, 195, 55, 138, 107, 113, 106, 77, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8