Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd32a22adb73564f49eb0af42c8f5e8359a3d464016155b6f1b718de41930a71

Tx prefix hash: ba69c9dbfed2fa3378c3d99cba31251f9528c82bebb2f097585f16ca79222b16
Tx public key: 65e559d0e8fdbe02cc52279e4aae04ec0fccd4d8ea893cf94628988fe14d4357
Timestamp: 1733754231 Timestamp [UCT]: 2024-12-09 14:23:51 Age [y:d:h:m:s]: 00:191:08:33:38
Block: 1171488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136468 RingCT/type: yes/0
Extra: 0165e559d0e8fdbe02cc52279e4aae04ec0fccd4d8ea893cf94628988fe14d4357021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d33d4618f32b13b04ad3d7fe447c024b6e15352d9a9e2b618ebb40c0a1db01a2 0.600000000000 1657251 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": 1171498, "vin": [ { "gen": { "height": 1171488 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d33d4618f32b13b04ad3d7fe447c024b6e15352d9a9e2b618ebb40c0a1db01a2" } } ], "extra": [ 1, 101, 229, 89, 208, 232, 253, 190, 2, 204, 82, 39, 158, 74, 174, 4, 236, 15, 204, 212, 216, 234, 137, 60, 249, 70, 40, 152, 143, 225, 77, 67, 87, 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