Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31bbf64f5fac08dc328b9f39b01dc1db65d1ebc7a5eef854e59c86c677ce5f23

Tx prefix hash: ac66949e1fe2e656f47e9dced47bbf4fca985b442e5335d7aee671b8e21c7fff
Tx public key: 0d27daaacb6dbc72c8ffbb3ea67c1f4da416408512b9ce400bdc06a9110150c8
Timestamp: 1714397955 Timestamp [UCT]: 2024-04-29 13:39:15 Age [y:d:h:m:s]: 00:256:06:10:29
Block: 1011108 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183421 RingCT/type: yes/0
Extra: 010d27daaacb6dbc72c8ffbb3ea67c1f4da416408512b9ce400bdc06a9110150c80211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fccda493fafa9e5b7265b6f69d83432b08789f5b1457b4dcded0c590800eed24 0.600000000000 1473248 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": 1011118, "vin": [ { "gen": { "height": 1011108 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fccda493fafa9e5b7265b6f69d83432b08789f5b1457b4dcded0c590800eed24" } } ], "extra": [ 1, 13, 39, 218, 170, 203, 109, 188, 114, 200, 255, 187, 62, 166, 124, 31, 77, 164, 22, 64, 133, 18, 185, 206, 64, 11, 220, 6, 169, 17, 1, 80, 200, 2, 17, 0, 0, 0, 6, 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