Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3b7d12f7b43c493b7640f57a6e359a20c52637fc2459d8f87b75ca080fa1eeb

Tx prefix hash: ce0e3970000f198d4b313fb5fe916f8bf684325e145c46c4ab29c104e19d37ec
Tx public key: 11d60d35894626c42a101dac68df7e2228dedb47f7cba7442d469402384252ce
Timestamp: 1714746895 Timestamp [UCT]: 2024-05-03 14:34:55 Age [y:d:h:m:s]: 00:253:05:30:58
Block: 1014009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181233 RingCT/type: yes/0
Extra: 0111d60d35894626c42a101dac68df7e2228dedb47f7cba7442d469402384252ce0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3993fb54b7a193f4dbaab6d8dc43d33e4ad47584fd6f528ca3ccdbdf4caa324 0.600000000000 1476980 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": 1014019, "vin": [ { "gen": { "height": 1014009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3993fb54b7a193f4dbaab6d8dc43d33e4ad47584fd6f528ca3ccdbdf4caa324" } } ], "extra": [ 1, 17, 214, 13, 53, 137, 70, 38, 196, 42, 16, 29, 172, 104, 223, 126, 34, 40, 222, 219, 71, 247, 203, 167, 68, 45, 70, 148, 2, 56, 66, 82, 206, 2, 17, 0, 0, 0, 4, 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