Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 483eed4c75e25cf86a1704bd6a543c95e1eb62c45a21b94d3d0eeb40847dd3e2

Tx prefix hash: 67649e20bec093ab502172981f27d727f21e736270f30632807c31d5ecfcac69
Tx public key: 5fcc5a9e227ec30660847c8fe784a0df3fd07fa2f22139f05e657d9be2bca6b6
Timestamp: 1740928671 Timestamp [UCT]: 2025-03-02 15:17:51 Age [y:d:h:m:s]: 00:309:07:25:29
Block: 1230602 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218903 RingCT/type: yes/0
Extra: 015fcc5a9e227ec30660847c8fe784a0df3fd07fa2f22139f05e657d9be2bca6b60211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ffcd9f24caa87b22a1af4011d83bd86b78b8f2207b251c6325cca6eebc543023 0.600000000000 1717501 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": 1230612, "vin": [ { "gen": { "height": 1230602 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ffcd9f24caa87b22a1af4011d83bd86b78b8f2207b251c6325cca6eebc543023" } } ], "extra": [ 1, 95, 204, 90, 158, 34, 126, 195, 6, 96, 132, 124, 143, 231, 132, 160, 223, 63, 208, 127, 162, 242, 33, 57, 240, 94, 101, 125, 155, 226, 188, 166, 182, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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