Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60d29e0db534bff7857d900339f397146521cf91a93e66cc6aa3ad21434c8aa6

Tx prefix hash: 218d1a5fcd4ec584a5c4ceb522f1124430b416a2ae9c65750ae26196982796a8
Tx public key: 08afb2f21786d03ea17bea54f06e5b8814021f5ffb35f03676fdd9d36e7d7ec3
Timestamp: 1729753015 Timestamp [UCT]: 2024-10-24 06:56:55 Age [y:d:h:m:s]: 00:090:14:59:46
Block: 1138386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64739 RingCT/type: yes/0
Extra: 0108afb2f21786d03ea17bea54f06e5b8814021f5ffb35f03676fdd9d36e7d7ec3021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 472dd5893c761380d3be261949dbbab57f1f9a5aaba0b70a821834e44890fb08 0.600000000000 1622039 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": 1138396, "vin": [ { "gen": { "height": 1138386 } } ], "vout": [ { "amount": 600000000, "target": { "key": "472dd5893c761380d3be261949dbbab57f1f9a5aaba0b70a821834e44890fb08" } } ], "extra": [ 1, 8, 175, 178, 242, 23, 134, 208, 62, 161, 123, 234, 84, 240, 110, 91, 136, 20, 2, 31, 95, 251, 53, 240, 54, 118, 253, 217, 211, 110, 125, 126, 195, 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