Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9243b8da83e5fbef112fe3a640d36d807b36fde48a60405a84864e65ca889b58

Tx prefix hash: 3f05eb77dd6858a3c91164fef3207d39f9568035dcf1c7385ca6a6565cee9c4f
Tx public key: 09ceb797ffb842699c4698bcb25480579360a4e8d9e08d65d08bf44ec4da30b4
Timestamp: 1713561230 Timestamp [UCT]: 2024-04-19 21:13:50 Age [y:d:h:m:s]: 00:354:11:11:23
Block: 1004156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253424 RingCT/type: yes/0
Extra: 0109ceb797ffb842699c4698bcb25480579360a4e8d9e08d65d08bf44ec4da30b402110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0688c6b1c03728cc98b9c4364a08cbe75c54da6e6cdf20fb8b3d28cc47e7c068 0.600000000000 1464724 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": 1004166, "vin": [ { "gen": { "height": 1004156 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0688c6b1c03728cc98b9c4364a08cbe75c54da6e6cdf20fb8b3d28cc47e7c068" } } ], "extra": [ 1, 9, 206, 183, 151, 255, 184, 66, 105, 156, 70, 152, 188, 178, 84, 128, 87, 147, 96, 164, 232, 217, 224, 141, 101, 208, 139, 244, 78, 196, 218, 48, 180, 2, 17, 0, 0, 0, 10, 122, 156, 244, 199, 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