Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b66ab92ef0b92ccbf27bf23c8c0f124a695daf1c201f8f4935a8ec319d1a4cb8

Tx prefix hash: 731f324b5718e22f81499bbabddffe7dabac2ac0f63246cb321ae4788fd265e1
Tx public key: 18a6963474df915cdb788ee3950bea8897578b01d4ac246cfc6fa518e8d46bb9
Timestamp: 1711834736 Timestamp [UCT]: 2024-03-30 21:38:56 Age [y:d:h:m:s]: 01:078:02:59:00
Block: 989876 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316720 RingCT/type: yes/0
Extra: 0118a6963474df915cdb788ee3950bea8897578b01d4ac246cfc6fa518e8d46bb90211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7cc37424515b70d111fd7d6b6c0e086c7cc4d83201cb40930f531189aac4a4a3 0.600000000000 1450194 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": 989886, "vin": [ { "gen": { "height": 989876 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7cc37424515b70d111fd7d6b6c0e086c7cc4d83201cb40930f531189aac4a4a3" } } ], "extra": [ 1, 24, 166, 150, 52, 116, 223, 145, 92, 219, 120, 142, 227, 149, 11, 234, 136, 151, 87, 139, 1, 212, 172, 36, 108, 252, 111, 165, 24, 232, 212, 107, 185, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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