Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 170b2aee7130e7601bc5df380e838917b548e6c75d5b61cb534da5336a515a57

Tx prefix hash: 317e9165ddea3bc7dd2678b6b17b2adac2ca3473d554082ea213508afbed994b
Tx public key: 219c10f6592a1cfeb37d8ac48752a193b449a4c94b9140117c6d3da59c056020
Timestamp: 1726236857 Timestamp [UCT]: 2024-09-13 14:14:17 Age [y:d:h:m:s]: 01:056:08:25:11
Block: 1109260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298688 RingCT/type: yes/0
Extra: 01219c10f6592a1cfeb37d8ac48752a193b449a4c94b9140117c6d3da59c05602002110000001e91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b05e1ea54a73f53f6c7ab87802d8b99559057b55b746e125b7df83e689e4f9d4 0.600000000000 1587447 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": 1109270, "vin": [ { "gen": { "height": 1109260 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b05e1ea54a73f53f6c7ab87802d8b99559057b55b746e125b7df83e689e4f9d4" } } ], "extra": [ 1, 33, 156, 16, 246, 89, 42, 28, 254, 179, 125, 138, 196, 135, 82, 161, 147, 180, 73, 164, 201, 75, 145, 64, 17, 124, 109, 61, 165, 156, 5, 96, 32, 2, 17, 0, 0, 0, 30, 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