Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f79cf9e880cd47767a124e3a8c22cdeab499827b1d568d73a4f0c6f79307a00d

Tx prefix hash: 0eed9457a44f41bbf262b4afdd2ef8c96a1e14de52b12ecdede0f9b522eb1aa5
Tx public key: 4ad17f9897bf237db7db57e7e2dcfe958f62613574ab36ceadcc01afa5bef1eb
Timestamp: 1736851233 Timestamp [UCT]: 2025-01-14 10:40:33 Age [y:d:h:m:s]: 00:061:19:23:31
Block: 1197113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43963 RingCT/type: yes/0
Extra: 014ad17f9897bf237db7db57e7e2dcfe958f62613574ab36ceadcc01afa5bef1eb021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48041304ae4e9af8e56d4c19981ee11d69475b58b98128f75cb6e76cc46934e1 0.600000000000 1683718 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": 1197123, "vin": [ { "gen": { "height": 1197113 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48041304ae4e9af8e56d4c19981ee11d69475b58b98128f75cb6e76cc46934e1" } } ], "extra": [ 1, 74, 209, 127, 152, 151, 191, 35, 125, 183, 219, 87, 231, 226, 220, 254, 149, 143, 98, 97, 53, 116, 171, 54, 206, 173, 204, 1, 175, 165, 190, 241, 235, 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