Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 539d730b258bdefe118c49c95fc091a43e5c93dfc1454ab9ab4a35684c1d0209

Tx prefix hash: 7012aaabfcfc3364d3aa07afcae2c68c123a95921da5377a680fdc8478a033e9
Tx public key: 63920213d712dc2e08fa68366021f97b3339d5a30a029f54d3447d05f5e8dfdc
Timestamp: 1713912612 Timestamp [UCT]: 2024-04-23 22:50:12 Age [y:d:h:m:s]: 00:281:06:49:57
Block: 1007086 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201064 RingCT/type: yes/0
Extra: 0163920213d712dc2e08fa68366021f97b3339d5a30a029f54d3447d05f5e8dfdc02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63ce6bed9b9c4b435b7007b3f1a55a255412d2f098fae18913a107f5273886fd 0.600000000000 1468316 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": 1007096, "vin": [ { "gen": { "height": 1007086 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63ce6bed9b9c4b435b7007b3f1a55a255412d2f098fae18913a107f5273886fd" } } ], "extra": [ 1, 99, 146, 2, 19, 215, 18, 220, 46, 8, 250, 104, 54, 96, 33, 249, 123, 51, 57, 213, 163, 10, 2, 159, 84, 211, 68, 125, 5, 245, 232, 223, 220, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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