Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d291fded4ce41291c6ef7784d46451bcda0219de82bc177c6dc67ecc70607b37

Tx prefix hash: 95df4f2c2055bf47e16cb842b4880fb57028db21d75c3fbdae47dd49f5523a9c
Tx public key: 277f2e57e86fad8ff35e89d984babf8b601b7a32e1d9523904bc4cee5b3014d1
Timestamp: 1704352562 Timestamp [UCT]: 2024-01-04 07:16:02 Age [y:d:h:m:s]: 01:073:05:16:40
Block: 927833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313437 RingCT/type: yes/0
Extra: 01277f2e57e86fad8ff35e89d984babf8b601b7a32e1d9523904bc4cee5b3014d10211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f1c921f320821fe70eea5483e54eea05b011f65623b03c041fe6fd65a47fb0b 0.600000000000 1385669 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": 927843, "vin": [ { "gen": { "height": 927833 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f1c921f320821fe70eea5483e54eea05b011f65623b03c041fe6fd65a47fb0b" } } ], "extra": [ 1, 39, 127, 46, 87, 232, 111, 173, 143, 243, 94, 137, 217, 132, 186, 191, 139, 96, 27, 122, 50, 225, 217, 82, 57, 4, 188, 76, 238, 91, 48, 20, 209, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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