Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41c614592cf36a8e01a13005e8d345654a0936880a7aee067f1d73823fed9831

Tx prefix hash: 837f8e254fbce1325ce47a7e00701237a75363c307604ceaa330ccde6a6b2b9a
Tx public key: 58a29d1dfcde68524a85c980390d9c6a994d68fefe814121978b954bbd831cb1
Timestamp: 1737505090 Timestamp [UCT]: 2025-01-22 00:18:10 Age [y:d:h:m:s]: 00:148:00:12:57
Block: 1202488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105520 RingCT/type: yes/0
Extra: 0158a29d1dfcde68524a85c980390d9c6a994d68fefe814121978b954bbd831cb10211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e3c87ae2ed9733a048d21e844b5a548f8be40b0b20c6e5afbc509cda541e3df 0.600000000000 1689153 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": 1202498, "vin": [ { "gen": { "height": 1202488 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e3c87ae2ed9733a048d21e844b5a548f8be40b0b20c6e5afbc509cda541e3df" } } ], "extra": [ 1, 88, 162, 157, 29, 252, 222, 104, 82, 74, 133, 201, 128, 57, 13, 156, 106, 153, 77, 104, 254, 254, 129, 65, 33, 151, 139, 149, 75, 189, 131, 28, 177, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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