Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b2f9c2ae29bc2af1c02288bb2d4eb3a20bf85c7f3323353abd908b78efe59d6

Tx prefix hash: 42ece76c6dab38009baf779dce3f9979bfe9ad60b8219287c01086c9c229c1ca
Tx public key: 2da49a1c719429cf86ecf06f8496d1f456070752a4af67d96acd1bbb097d3782
Timestamp: 1710869232 Timestamp [UCT]: 2024-03-19 17:27:12 Age [y:d:h:m:s]: 01:051:21:50:35
Block: 981878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298082 RingCT/type: yes/0
Extra: 012da49a1c719429cf86ecf06f8496d1f456070752a4af67d96acd1bbb097d37820211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61df7ef776267dc8e158a323510c75064573069bfd9e3bf0aaa8e6b0cbef91fc 0.600000000000 1441979 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": 981888, "vin": [ { "gen": { "height": 981878 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61df7ef776267dc8e158a323510c75064573069bfd9e3bf0aaa8e6b0cbef91fc" } } ], "extra": [ 1, 45, 164, 154, 28, 113, 148, 41, 207, 134, 236, 240, 111, 132, 150, 209, 244, 86, 7, 7, 82, 164, 175, 103, 217, 106, 205, 27, 187, 9, 125, 55, 130, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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