Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97e5e02cd7984ff365b205632652dce80334dfff46d80eb3ea2b6f89f92e2332

Tx prefix hash: b55adae5e8e3aec65873eafd6428bec92e3ffb56917fe101db03309f7c37bd69
Tx public key: 432e03e3310f2d96bf12401d0a67039c435bc025b76dfdf0c1dfd2a53af4fe0c
Timestamp: 1737553561 Timestamp [UCT]: 2025-01-22 13:46:01 Age [y:d:h:m:s]: 00:147:00:24:59
Block: 1202895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104801 RingCT/type: yes/0
Extra: 01432e03e3310f2d96bf12401d0a67039c435bc025b76dfdf0c1dfd2a53af4fe0c021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9cdfd30f37fd40233c937cd21c61a66bb42cb62aecfdd4e698e8f28fe52d301 0.600000000000 1689562 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": 1202905, "vin": [ { "gen": { "height": 1202895 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9cdfd30f37fd40233c937cd21c61a66bb42cb62aecfdd4e698e8f28fe52d301" } } ], "extra": [ 1, 67, 46, 3, 227, 49, 15, 45, 150, 191, 18, 64, 29, 10, 103, 3, 156, 67, 91, 192, 37, 183, 109, 253, 240, 193, 223, 210, 165, 58, 244, 254, 12, 2, 17, 0, 0, 0, 3, 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