Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e384ed1e14f9a72610d7bf44e23589b15fcc36a716178f553237e8ea5d6ed8d

Tx prefix hash: fca108e7bcbe5ca114a280e6eac4ea41ace892ff9ddcaa12151e1af8c509354a
Tx public key: d55159a1837713c716604bdb36ea10f72824b8cab3269ba5764bcfba7b045d8f
Timestamp: 1734112396 Timestamp [UCT]: 2024-12-13 17:53:16 Age [y:d:h:m:s]: 00:101:15:38:34
Block: 1174467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72415 RingCT/type: yes/0
Extra: 01d55159a1837713c716604bdb36ea10f72824b8cab3269ba5764bcfba7b045d8f021100000001e890f369000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b85a7c5a18352848ea94e4eed1a5e153f90da3b3b0540428940d4453ab5cf3b7 0.600000000000 1660622 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": 1174477, "vin": [ { "gen": { "height": 1174467 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b85a7c5a18352848ea94e4eed1a5e153f90da3b3b0540428940d4453ab5cf3b7" } } ], "extra": [ 1, 213, 81, 89, 161, 131, 119, 19, 199, 22, 96, 75, 219, 54, 234, 16, 247, 40, 36, 184, 202, 179, 38, 155, 165, 118, 75, 207, 186, 123, 4, 93, 143, 2, 17, 0, 0, 0, 1, 232, 144, 243, 105, 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