Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77a36837d5c59e37a70cf32718ac1db0b268eb35155363a5d59863703c99fb9f

Tx prefix hash: 566b980823aadf13aefd6354adc9914833ad61e829cda385b4033131709e9362
Tx public key: d99c052b938a6147e4f02791ad37108239a7b9de3049b8ee00a8cdc859fdafa8
Timestamp: 1719121712 Timestamp [UCT]: 2024-06-23 05:48:32 Age [y:d:h:m:s]: 00:265:03:33:08
Block: 1050256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189491 RingCT/type: yes/0
Extra: 01d99c052b938a6147e4f02791ad37108239a7b9de3049b8ee00a8cdc859fdafa802110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c10ee6e69c1362c830fefb47f2b9cb80ba5e5ac17706847b8dcab48beae0e0e 0.600000000000 1520417 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": 1050266, "vin": [ { "gen": { "height": 1050256 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c10ee6e69c1362c830fefb47f2b9cb80ba5e5ac17706847b8dcab48beae0e0e" } } ], "extra": [ 1, 217, 156, 5, 43, 147, 138, 97, 71, 228, 240, 39, 145, 173, 55, 16, 130, 57, 167, 185, 222, 48, 73, 184, 238, 0, 168, 205, 200, 89, 253, 175, 168, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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