Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06eea8b33dd17e1836be1227a0eceebed4e886d43df71ed713a2411b4ed9d2df

Tx prefix hash: 02e4ec28b9deab9e9eef2c56775726446476451410049e6391099f6a387a2bff
Tx public key: 3abb732c28a34cf2b6941f00086c737ce1c5b04eaf4c1c73aa0ad6ee8a448743
Timestamp: 1704276703 Timestamp [UCT]: 2024-01-03 10:11:43 Age [y:d:h:m:s]: 01:305:21:31:57
Block: 927205 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477441 RingCT/type: yes/0
Extra: 013abb732c28a34cf2b6941f00086c737ce1c5b04eaf4c1c73aa0ad6ee8a44874302110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c7f991fc32ae9547ffc50c60b88ecfb10dcfe6c05259310a8a3f719201a205c 0.600000000000 1385011 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": 927215, "vin": [ { "gen": { "height": 927205 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c7f991fc32ae9547ffc50c60b88ecfb10dcfe6c05259310a8a3f719201a205c" } } ], "extra": [ 1, 58, 187, 115, 44, 40, 163, 76, 242, 182, 148, 31, 0, 8, 108, 115, 124, 225, 197, 176, 78, 175, 76, 28, 115, 170, 10, 214, 238, 138, 68, 135, 67, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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