Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55bbd0ca650c1cec568e0fdaebf7cb624bcf7bf52442fe695bf02c0460bf3cd5

Tx prefix hash: f4d17841fa25d6fe82f64368b6f456924683eacd7563dea9eac603e90585e0da
Tx public key: 97923eb6964acbe5728aa2d4481636afbf6c08aefb9c3e11df04ded0cb858e1d
Timestamp: 1726692319 Timestamp [UCT]: 2024-09-18 20:45:19 Age [y:d:h:m:s]: 00:176:18:41:56
Block: 1113039 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126170 RingCT/type: yes/0
Extra: 0197923eb6964acbe5728aa2d4481636afbf6c08aefb9c3e11df04ded0cb858e1d02110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3dae41b3b34606f7a7c08b60496b0e922b30e8b4de2df073fa30740583ca749 0.600000000000 1592570 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": 1113049, "vin": [ { "gen": { "height": 1113039 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3dae41b3b34606f7a7c08b60496b0e922b30e8b4de2df073fa30740583ca749" } } ], "extra": [ 1, 151, 146, 62, 182, 150, 74, 203, 229, 114, 138, 162, 212, 72, 22, 54, 175, 191, 108, 8, 174, 251, 156, 62, 17, 223, 4, 222, 208, 203, 133, 142, 29, 2, 17, 0, 0, 0, 9, 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