Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c07d57e68955fb07d9da4539f7acabaa7bf077254cb4d010feaa479baa7193be

Tx prefix hash: 046e2173d3d9495b2bf4cc21cf18a1e5e325c5845a47a38784544d7abede0294
Tx public key: 5c1435872438ba5a2b5c6a320a8ecca3c3ebb8622d6e2da54f4bd508f97a8a8c
Timestamp: 1634053210 Timestamp [UCT]: 2021-10-12 15:40:10 Age [y:d:h:m:s]: 03:199:07:52:48
Block: 351754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 919877 RingCT/type: yes/0
Extra: 015c1435872438ba5a2b5c6a320a8ecca3c3ebb8622d6e2da54f4bd508f97a8a8c02110000000b8d0de867000000000000000000

1 output(s) for total of 41.926962336000 dcy

stealth address amount amount idx
00: 2a66913c5abd822ccde4dbfdcf5c4fb3e6a7f80ed2b616bc019f7f9becb46ece 41.926962336000 719204 of 0

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": 351764, "vin": [ { "gen": { "height": 351754 } } ], "vout": [ { "amount": 41926962336, "target": { "key": "2a66913c5abd822ccde4dbfdcf5c4fb3e6a7f80ed2b616bc019f7f9becb46ece" } } ], "extra": [ 1, 92, 20, 53, 135, 36, 56, 186, 90, 43, 92, 106, 50, 10, 142, 204, 163, 195, 235, 184, 98, 45, 110, 45, 165, 79, 75, 213, 8, 249, 122, 138, 140, 2, 17, 0, 0, 0, 11, 141, 13, 232, 103, 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