Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ba822c1f004e8f9d203655e3e13af4a5aa7acaf05480efd3b37ce354e9f6221

Tx prefix hash: 904e6f9741b7f18993e96bfee17ea300275f4c01ae5c3e7548c7a1d568f2aed0
Tx public key: 363cd46064ac7d9e9c58fdc2cb590cbb28fcc06914102be0a9ad0679af76d20f
Timestamp: 1704813542 Timestamp [UCT]: 2024-01-09 15:19:02 Age [y:d:h:m:s]: 01:108:06:46:39
Block: 931642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338509 RingCT/type: yes/0
Extra: 01363cd46064ac7d9e9c58fdc2cb590cbb28fcc06914102be0a9ad0679af76d20f0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79037cf2e88407c721b71dc286edeafb2dca9435a60c3d8ba75e0a768b6094e9 0.600000000000 1389546 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": 931652, "vin": [ { "gen": { "height": 931642 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79037cf2e88407c721b71dc286edeafb2dca9435a60c3d8ba75e0a768b6094e9" } } ], "extra": [ 1, 54, 60, 212, 96, 100, 172, 125, 158, 156, 88, 253, 194, 203, 89, 12, 187, 40, 252, 192, 105, 20, 16, 43, 224, 169, 173, 6, 121, 175, 118, 210, 15, 2, 17, 0, 0, 0, 7, 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