Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a656fb1ee67c8dc96b648ff3b5bd4229a5ba35b9e942eda8fb46ad2640b41419

Tx prefix hash: e05bb4438637f94724e5b69a1e3821588a414074efbe8e78912c6c0ca0864a7d
Tx public key: 773d465e22e3d539e406161148dd5f1f1e4917bbfd42ac6a7dbe522b797afade
Timestamp: 1726435376 Timestamp [UCT]: 2024-09-15 21:22:56 Age [y:d:h:m:s]: 00:116:20:50:06
Block: 1110909 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83572 RingCT/type: yes/0
Extra: 01773d465e22e3d539e406161148dd5f1f1e4917bbfd42ac6a7dbe522b797afade021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9cbc045b4043956f6d2a9fe56c2745e0886735c4e6cada4c8f28772ab4e7b85 0.600000000000 1589682 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": 1110919, "vin": [ { "gen": { "height": 1110909 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9cbc045b4043956f6d2a9fe56c2745e0886735c4e6cada4c8f28772ab4e7b85" } } ], "extra": [ 1, 119, 61, 70, 94, 34, 227, 213, 57, 228, 6, 22, 17, 72, 221, 95, 31, 30, 73, 23, 187, 253, 66, 172, 106, 125, 190, 82, 43, 121, 122, 250, 222, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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