Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e250e30df40bae5319636c560f117d97823bc088c563d5937538a6c289c4db43

Tx prefix hash: 20f3626b50adf7728aa2a2c5fb3314ab9a715fc3a1c3892ec97628f75d33ce86
Tx public key: ac84319818ad87f2c0af88a2f8e48da083c4455bda9b3585ab37a29376a4b7d5
Timestamp: 1705905218 Timestamp [UCT]: 2024-01-22 06:33:38 Age [y:d:h:m:s]: 01:072:05:58:07
Block: 940661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312744 RingCT/type: yes/0
Extra: 01ac84319818ad87f2c0af88a2f8e48da083c4455bda9b3585ab37a29376a4b7d50211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a30fd5c832ce42bbc05ca461be6739457269966a0cefa79a28cc2b363acc8b37 0.600000000000 1398801 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": 940671, "vin": [ { "gen": { "height": 940661 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a30fd5c832ce42bbc05ca461be6739457269966a0cefa79a28cc2b363acc8b37" } } ], "extra": [ 1, 172, 132, 49, 152, 24, 173, 135, 242, 192, 175, 136, 162, 248, 228, 141, 160, 131, 196, 69, 91, 218, 155, 53, 133, 171, 55, 162, 147, 118, 164, 183, 213, 2, 17, 0, 0, 0, 1, 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