Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7bbce23dbbce4710012bf9ab2fa0f1133cc1415a0be09713407847a18181f3fb

Tx prefix hash: 0c15970bcd71212ed26b32d0a80c0eb319c1c13ebf368a004cd71191cf105316
Tx public key: 4a5223a5eaa0b2368d13ded76d67a5332b9784d2fa4fa2f8a05647e246f109e4
Timestamp: 1731755151 Timestamp [UCT]: 2024-11-16 11:05:51 Age [y:d:h:m:s]: 00:217:15:53:26
Block: 1154929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155237 RingCT/type: yes/0
Extra: 014a5223a5eaa0b2368d13ded76d67a5332b9784d2fa4fa2f8a05647e246f109e402110000000c1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19b373f54d1d9684ff42a7cfca730fa1cffd8834de63c3167bb9453e17c52f31 0.600000000000 1640542 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": 1154939, "vin": [ { "gen": { "height": 1154929 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19b373f54d1d9684ff42a7cfca730fa1cffd8834de63c3167bb9453e17c52f31" } } ], "extra": [ 1, 74, 82, 35, 165, 234, 160, 178, 54, 141, 19, 222, 215, 109, 103, 165, 51, 43, 151, 132, 210, 250, 79, 162, 248, 160, 86, 71, 226, 70, 241, 9, 228, 2, 17, 0, 0, 0, 12, 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