Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d675eca4203c87027b1b9866e717a267adf3ab501dfaa4c554168128c9f60146

Tx prefix hash: 553a9516f1b61f7e2100155f52bace5983be7df039b2fa4aea0471a6558756b7
Tx public key: 7c9de60c7085f8cae8044f2d07ab4fad76f11211296e59bbef73d09ffb05d5bb
Timestamp: 1732853726 Timestamp [UCT]: 2024-11-29 04:15:26 Age [y:d:h:m:s]: 00:154:07:17:09
Block: 1164019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110106 RingCT/type: yes/0
Extra: 017c9de60c7085f8cae8044f2d07ab4fad76f11211296e59bbef73d09ffb05d5bb021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9c849b7a022bcc51e6f11db613e7a628bc2f9f9bdc42e3ede4380fb09808518 0.600000000000 1649690 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": 1164029, "vin": [ { "gen": { "height": 1164019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9c849b7a022bcc51e6f11db613e7a628bc2f9f9bdc42e3ede4380fb09808518" } } ], "extra": [ 1, 124, 157, 230, 12, 112, 133, 248, 202, 232, 4, 79, 45, 7, 171, 79, 173, 118, 241, 18, 17, 41, 110, 89, 187, 239, 115, 208, 159, 251, 5, 213, 187, 2, 17, 0, 0, 0, 1, 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