Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9a35430f24efa5b3d7d0ffdd1915fb4ed105278d4296548d232579ae7c90823

Tx prefix hash: d59569f3dc69d60aa350fae3e613f0123dfe1e9ce64f36efa55e099ad043d710
Tx public key: d114eb83377b6dcfe1f8b915f15979e4f040e23ec76ab4dc4fa873bd001beecb
Timestamp: 1720930383 Timestamp [UCT]: 2024-07-14 04:13:03 Age [y:d:h:m:s]: 00:253:13:29:26
Block: 1065282 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181128 RingCT/type: yes/0
Extra: 01d114eb83377b6dcfe1f8b915f15979e4f040e23ec76ab4dc4fa873bd001beecb02110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0749434a0df9f5cf50652ae347538366946bb5aec2b9139ac47ae676cd879c3 0.600000000000 1535827 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": 1065292, "vin": [ { "gen": { "height": 1065282 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0749434a0df9f5cf50652ae347538366946bb5aec2b9139ac47ae676cd879c3" } } ], "extra": [ 1, 209, 20, 235, 131, 55, 123, 109, 207, 225, 248, 185, 21, 241, 89, 121, 228, 240, 64, 226, 62, 199, 106, 180, 220, 79, 168, 115, 189, 0, 27, 238, 203, 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