Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e17c95b0003662f4776f00ceff2f0c3a4bc46e8220e43469563d599565cdf85

Tx prefix hash: 6d0722fbf52b3c964b69c89f79b4e7c97e6b3dd49ae71f676d42d004c1e48e5e
Tx public key: 3770ceb033e999fca711f9afc48e23a398e9d1e28b874a8cdf91597906861021
Timestamp: 1740238790 Timestamp [UCT]: 2025-02-22 15:39:50 Age [y:d:h:m:s]: 00:228:07:04:45
Block: 1224868 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160881 RingCT/type: yes/0
Extra: 013770ceb033e999fca711f9afc48e23a398e9d1e28b874a8cdf91597906861021021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e47f3d7eb354f21f79c2336ccdba09347bb4d6cc4c339a56c25b3a432615b1e0 0.600000000000 1711731 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": 1224878, "vin": [ { "gen": { "height": 1224868 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e47f3d7eb354f21f79c2336ccdba09347bb4d6cc4c339a56c25b3a432615b1e0" } } ], "extra": [ 1, 55, 112, 206, 176, 51, 233, 153, 252, 167, 17, 249, 175, 196, 142, 35, 163, 152, 233, 209, 226, 139, 135, 74, 140, 223, 145, 89, 121, 6, 134, 16, 33, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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