Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8c5c5effa0172d7722f41a2089e1b35f299bb125919ed18b85954295295f527

Tx prefix hash: a82e42554a520423f81bf9518c9636e97a2de4d3bed24a4b34701a4ef4f2375e
Tx public key: afc7074c3327e8a2a921df6e7c97a8d9cb0b67a2f36e79030754cf56e0930d83
Timestamp: 1730048631 Timestamp [UCT]: 2024-10-27 17:03:51 Age [y:d:h:m:s]: 00:139:10:02:57
Block: 1140826 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99446 RingCT/type: yes/0
Extra: 01afc7074c3327e8a2a921df6e7c97a8d9cb0b67a2f36e79030754cf56e0930d83021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07376fae6be81f2e0293ab04f0554f799d547b687b2721fa740313306ed16608 0.600000000000 1624629 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": 1140836, "vin": [ { "gen": { "height": 1140826 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07376fae6be81f2e0293ab04f0554f799d547b687b2721fa740313306ed16608" } } ], "extra": [ 1, 175, 199, 7, 76, 51, 39, 232, 162, 169, 33, 223, 110, 124, 151, 168, 217, 203, 11, 103, 162, 243, 110, 121, 3, 7, 84, 207, 86, 224, 147, 13, 131, 2, 17, 0, 0, 0, 1, 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