Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49f16a805ab91222ff0b5bada4cc45504f73eba987cf6a41db197ec4279c123f

Tx prefix hash: cebdf664f9ea66dc1ffb2ed5fe344759cfd869c3a96f0ee7cecce6d3b02fe9f7
Tx public key: 3c52b29bb94d910aeec74c358c8b35d8dc14fbd7065e205e8fb310523acc3bc2
Timestamp: 1732344517 Timestamp [UCT]: 2024-11-23 06:48:37 Age [y:d:h:m:s]: 00:000:15:41:11
Block: 1159803 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 462 RingCT/type: yes/0
Extra: 013c52b29bb94d910aeec74c358c8b35d8dc14fbd7065e205e8fb310523acc3bc2021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14b3f3cd69b25f841337e45a5b13181b57263486401146e4ffd7a2dd0f95c199 0.600000000000 1645442 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": 1159813, "vin": [ { "gen": { "height": 1159803 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14b3f3cd69b25f841337e45a5b13181b57263486401146e4ffd7a2dd0f95c199" } } ], "extra": [ 1, 60, 82, 178, 155, 185, 77, 145, 10, 238, 199, 76, 53, 140, 139, 53, 216, 220, 20, 251, 215, 6, 94, 32, 94, 143, 179, 16, 82, 58, 204, 59, 194, 2, 17, 0, 0, 0, 9, 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