Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13971162b079c124a65352a432e6c6da5d54d1da90065f5251de43c9cecbf12e

Tx prefix hash: 4c885e1a19f214bc8f31bae950fcf37b9ac672f6d9c474796c4b23d160ad1c5d
Tx public key: 6dfb6f4b2326fb35f1a8c75733781cb137a8dcf8ab8e28e60d0b56244f351165
Timestamp: 1720605050 Timestamp [UCT]: 2024-07-10 09:50:50 Age [y:d:h:m:s]: 00:266:22:34:58
Block: 1062577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190705 RingCT/type: yes/0
Extra: 016dfb6f4b2326fb35f1a8c75733781cb137a8dcf8ab8e28e60d0b56244f35116502110000000e91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d5dbc0e0c823d6de5c1edc9f1a29665840576a7afc29c73169cb5cd1c9e42c4 0.600000000000 1533082 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": 1062587, "vin": [ { "gen": { "height": 1062577 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d5dbc0e0c823d6de5c1edc9f1a29665840576a7afc29c73169cb5cd1c9e42c4" } } ], "extra": [ 1, 109, 251, 111, 75, 35, 38, 251, 53, 241, 168, 199, 87, 51, 120, 28, 177, 55, 168, 220, 248, 171, 142, 40, 230, 13, 11, 86, 36, 79, 53, 17, 101, 2, 17, 0, 0, 0, 14, 145, 225, 60, 4, 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