Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5931fead3791659716ea8156c52e67bb6fbb977beb82c6410eacc7a20fa2f2cb

Tx prefix hash: 2c506f288aebf41136f707e0ce66f88c59073b6d0181e7d2d646e50fc46595e2
Tx public key: 9e04763d420c6d28ae4b9ce88ada3ef9bd53c8150aa63e55b8a1b1991b048319
Timestamp: 1734059644 Timestamp [UCT]: 2024-12-13 03:14:04 Age [y:d:h:m:s]: 00:099:09:11:45
Block: 1174026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70803 RingCT/type: yes/0
Extra: 019e04763d420c6d28ae4b9ce88ada3ef9bd53c8150aa63e55b8a1b1991b048319021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6d3b2e08354555f9461bf646da78df0893555ad8cdd3ae85d0b825596ab4706 0.600000000000 1660125 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": 1174036, "vin": [ { "gen": { "height": 1174026 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6d3b2e08354555f9461bf646da78df0893555ad8cdd3ae85d0b825596ab4706" } } ], "extra": [ 1, 158, 4, 118, 61, 66, 12, 109, 40, 174, 75, 156, 232, 138, 218, 62, 249, 189, 83, 200, 21, 10, 166, 62, 85, 184, 161, 177, 153, 27, 4, 131, 25, 2, 17, 0, 0, 0, 3, 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