Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b95e059c3d7208b7508aecd75d1421b334463f50b3a2206f7650e668bf3d662c

Tx prefix hash: 7e16f112d02131a42532daa5e9d4987c5da831df9c293f5e50176562ddd4f553
Tx public key: 975f79ec77faadd1ed4ea80cb33a04f0c7b09e6862afb9999d0ffe0ec9c6e786
Timestamp: 1710563501 Timestamp [UCT]: 2024-03-16 04:31:41 Age [y:d:h:m:s]: 01:021:05:34:40
Block: 979342 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276145 RingCT/type: yes/0
Extra: 01975f79ec77faadd1ed4ea80cb33a04f0c7b09e6862afb9999d0ffe0ec9c6e78602110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41c4a41a6cf3391fa9ce57926f8f5e4fe133bb04e532e64130bc6aa79fe67238 0.600000000000 1439375 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": 979352, "vin": [ { "gen": { "height": 979342 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41c4a41a6cf3391fa9ce57926f8f5e4fe133bb04e532e64130bc6aa79fe67238" } } ], "extra": [ 1, 151, 95, 121, 236, 119, 250, 173, 209, 237, 78, 168, 12, 179, 58, 4, 240, 199, 176, 158, 104, 98, 175, 185, 153, 157, 15, 254, 14, 201, 198, 231, 134, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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