Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a376c8885054a257aa44d1856830c9ed4162d2824227a83a8f2a04d4c610e06

Tx prefix hash: 0ed9b4f74a66eaf8eac0f31c504b698d8771318f3e005574c969f88dab2ae1a2
Tx public key: 4633e047ac3c62759e9820d698993b31f647e379e1734fe5cd201cb4929d4dee
Timestamp: 1725157046 Timestamp [UCT]: 2024-09-01 02:17:26 Age [y:d:h:m:s]: 01:060:06:26:10
Block: 1100306 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301510 RingCT/type: yes/0
Extra: 014633e047ac3c62759e9820d698993b31f647e379e1734fe5cd201cb4929d4dee02110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47fc71334f7afdcd5fec158cc8a93891b5bd08f76bd1c97ecf409bf78133a317 0.600000000000 1576281 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": 1100316, "vin": [ { "gen": { "height": 1100306 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47fc71334f7afdcd5fec158cc8a93891b5bd08f76bd1c97ecf409bf78133a317" } } ], "extra": [ 1, 70, 51, 224, 71, 172, 60, 98, 117, 158, 152, 32, 214, 152, 153, 59, 49, 246, 71, 227, 121, 225, 115, 79, 229, 205, 32, 28, 180, 146, 157, 77, 238, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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