Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8b0fa5b14014c8cbf81bc5887fd64180b7e9811841b4c0ec8456b17cfd83854

Tx prefix hash: 3183bea2ab12f83bf4c935318b0e95d735a29aaf897e10b7d3a47a53660d8a5b
Tx public key: 35bc28ad69fce9fb97c02ac0b8a1ec9672eb734443062cf7d1ecada1bd4906b8
Timestamp: 1702372364 Timestamp [UCT]: 2023-12-12 09:12:44 Age [y:d:h:m:s]: 01:146:20:34:02
Block: 911422 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366105 RingCT/type: yes/0
Extra: 0135bc28ad69fce9fb97c02ac0b8a1ec9672eb734443062cf7d1ecada1bd4906b802110000000675e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c02511ee7df5544f7353bcd365bccf8c333711a17f131c9c8f44d85e5029c496 0.600000000000 1368624 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": 911432, "vin": [ { "gen": { "height": 911422 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c02511ee7df5544f7353bcd365bccf8c333711a17f131c9c8f44d85e5029c496" } } ], "extra": [ 1, 53, 188, 40, 173, 105, 252, 233, 251, 151, 192, 42, 192, 184, 161, 236, 150, 114, 235, 115, 68, 67, 6, 44, 247, 209, 236, 173, 161, 189, 73, 6, 184, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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