Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3c646f2ae7eee904affaaf7acebf95fa7d6df7c11c38d6b8119dbd969b0e465

Tx prefix hash: 9c6587cd46a01a9a202b45d49365dce7b3904407c024d90454a91428ae67a9e9
Tx public key: 1c073f838dfe8eb842ef0bf46a64280fd655dbf378b3f7f20f15a40e896a5fc2
Timestamp: 1732369702 Timestamp [UCT]: 2024-11-23 13:48:22 Age [y:d:h:m:s]: 00:195:13:48:39
Block: 1159999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139643 RingCT/type: yes/0
Extra: 011c073f838dfe8eb842ef0bf46a64280fd655dbf378b3f7f20f15a40e896a5fc2021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0846d5ed5688593843c8bf9dd09aa946f66cfccbde2da91b4b8bb6d9a354ea40 0.600000000000 1645640 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": 1160009, "vin": [ { "gen": { "height": 1159999 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0846d5ed5688593843c8bf9dd09aa946f66cfccbde2da91b4b8bb6d9a354ea40" } } ], "extra": [ 1, 28, 7, 63, 131, 141, 254, 142, 184, 66, 239, 11, 244, 106, 100, 40, 15, 214, 85, 219, 243, 120, 179, 247, 242, 15, 21, 164, 14, 137, 106, 95, 194, 2, 17, 0, 0, 0, 2, 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