Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f18f470b8a1ba03b91e94722dbdc0740936ba01858493717a476b22da4c9c09b

Tx prefix hash: 64f665adc8fe7a721f35dc60cec072e477d721575f1a233a15ef1bf537c478e5
Tx public key: 536f1ffe12166b64fa1c7de457e99e296fc407dce91c690e0e0ddd680eb521db
Timestamp: 1706412280 Timestamp [UCT]: 2024-01-28 03:24:40 Age [y:d:h:m:s]: 01:080:13:05:22
Block: 944880 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318656 RingCT/type: yes/0
Extra: 01536f1ffe12166b64fa1c7de457e99e296fc407dce91c690e0e0ddd680eb521db02110000000210a1748f000000000000000000

1 output(s) for total of 0.600010000000 dcy

stealth address amount amount idx
00: 8364ac8e0ebba27a23a2c09017052a270b6dca7c84eaf5aa4b6cd3ae4b7bdf34 0.600010000000 1403172 of 0

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": 944890, "vin": [ { "gen": { "height": 944880 } } ], "vout": [ { "amount": 600010000, "target": { "key": "8364ac8e0ebba27a23a2c09017052a270b6dca7c84eaf5aa4b6cd3ae4b7bdf34" } } ], "extra": [ 1, 83, 111, 31, 254, 18, 22, 107, 100, 250, 28, 125, 228, 87, 233, 158, 41, 111, 196, 7, 220, 233, 28, 105, 14, 14, 13, 221, 104, 14, 181, 33, 219, 2, 17, 0, 0, 0, 2, 16, 161, 116, 143, 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