Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4473801e850005987b31c0869132b4dd6424f052c4e156873dd667ebd9c6167a

Tx prefix hash: 195fdbd968c05b0b829089b2a9c8fefe4945ac4d4a10e40d4fc226e3c2f2bd36
Tx public key: 7bfa56d85b208f1cc0dca0d6e186ed58d0d010a989f4542a7bc62e69eb74498b
Timestamp: 1708275170 Timestamp [UCT]: 2024-02-18 16:52:50 Age [y:d:h:m:s]: 01:268:03:15:05
Block: 960348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 450395 RingCT/type: yes/0
Extra: 017bfa56d85b208f1cc0dca0d6e186ed58d0d010a989f4542a7bc62e69eb74498b0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c6f90654cbf783c9a2b786fe04aa7f99ead5eb116fa31425291de08ce992a1b 0.600000000000 1419911 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": 960358, "vin": [ { "gen": { "height": 960348 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c6f90654cbf783c9a2b786fe04aa7f99ead5eb116fa31425291de08ce992a1b" } } ], "extra": [ 1, 123, 250, 86, 216, 91, 32, 143, 28, 192, 220, 160, 214, 225, 134, 237, 88, 208, 208, 16, 169, 137, 244, 84, 42, 123, 198, 46, 105, 235, 116, 73, 139, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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