Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9db11dd42b6f0e5b1ea0051306d8aa6d6a9a89bb47f8c1335a1215262f972fef

Tx prefix hash: 275dcb16f2d8bd8178d37a852bdd1bd3e2b71334a146e2bfebd0072f58323222
Tx public key: 0228101de9611926b7827a48ccec1e1add3203425a12c4a06de8e5833ed1104c
Timestamp: 1717059181 Timestamp [UCT]: 2024-05-30 08:53:01 Age [y:d:h:m:s]: 00:322:13:10:54
Block: 1033170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230526 RingCT/type: yes/0
Extra: 010228101de9611926b7827a48ccec1e1add3203425a12c4a06de8e5833ed1104c02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: acc3c852a837c8a582f35b2f58e1cd395649b3e320b048a661bf0d18f55c7a3b 0.600000000000 1501633 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": 1033180, "vin": [ { "gen": { "height": 1033170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "acc3c852a837c8a582f35b2f58e1cd395649b3e320b048a661bf0d18f55c7a3b" } } ], "extra": [ 1, 2, 40, 16, 29, 233, 97, 25, 38, 183, 130, 122, 72, 204, 236, 30, 26, 221, 50, 3, 66, 90, 18, 196, 160, 109, 232, 229, 131, 62, 209, 16, 76, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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