Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fa2d3256ee0ae1207b4e2293dcea2ece4bfeed786040c86b50583e3eb6d0240

Tx prefix hash: 469e74225960a7d077ec035237c312122cdc969515a58376928a6a411b2f65cd
Tx public key: 4318a76d2fb6a264f0fcb91a248d7406ea6f096018694e0fe14ef6cb6b460a09
Timestamp: 1719072731 Timestamp [UCT]: 2024-06-22 16:12:11 Age [y:d:h:m:s]: 01:139:04:55:04
Block: 1049849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358056 RingCT/type: yes/0
Extra: 014318a76d2fb6a264f0fcb91a248d7406ea6f096018694e0fe14ef6cb6b460a0902110000004052d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 372a147ac743e3fcdbdd6c18bc42ed3a1618e713fcde0bbe0c435d5ea1d33eff 0.600000000000 1519954 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": 1049859, "vin": [ { "gen": { "height": 1049849 } } ], "vout": [ { "amount": 600000000, "target": { "key": "372a147ac743e3fcdbdd6c18bc42ed3a1618e713fcde0bbe0c435d5ea1d33eff" } } ], "extra": [ 1, 67, 24, 167, 109, 47, 182, 162, 100, 240, 252, 185, 26, 36, 141, 116, 6, 234, 111, 9, 96, 24, 105, 78, 15, 225, 78, 246, 203, 107, 70, 10, 9, 2, 17, 0, 0, 0, 64, 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