Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a501e67566d357bbc0ef4c6053e863e33976c2195e36c4fb638d5c6b7039aebb

Tx prefix hash: e42545188d78d6dd854739c1aae6294efbcdb9487a9668735d0a038e6c7166f6
Tx public key: 31e18b41c0f88f0a1b6bcbe8b61c41f2db04afc1551557c9d9eecca054802320
Timestamp: 1737126769 Timestamp [UCT]: 2025-01-17 15:12:49 Age [y:d:h:m:s]: 00:307:06:46:43
Block: 1199388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217130 RingCT/type: yes/0
Extra: 0131e18b41c0f88f0a1b6bcbe8b61c41f2db04afc1551557c9d9eecca05480232002110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bda43f480692c39cfb355da62501ea74f45b6ef75c624b87ef7ed25dccf3764b 0.600000000000 1686019 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": 1199398, "vin": [ { "gen": { "height": 1199388 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bda43f480692c39cfb355da62501ea74f45b6ef75c624b87ef7ed25dccf3764b" } } ], "extra": [ 1, 49, 225, 139, 65, 192, 248, 143, 10, 27, 107, 203, 232, 182, 28, 65, 242, 219, 4, 175, 193, 85, 21, 87, 201, 217, 238, 204, 160, 84, 128, 35, 32, 2, 17, 0, 0, 0, 10, 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