Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d8dc7c1d89b45c1a98f9bea48fc157f187542c0aa42348a5236745db6ce007f

Tx prefix hash: 5b1ee8cf3d76516871c0e9da1c8fadb3e4906a7f603c9220acfe822800f333e2
Tx public key: 77461419efb2fe8a9fe420f23be4846d187d0a8911bfa81cf831e62837a826ae
Timestamp: 1714629753 Timestamp [UCT]: 2024-05-02 06:02:33 Age [y:d:h:m:s]: 00:299:01:15:52
Block: 1013035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213737 RingCT/type: yes/0
Extra: 0177461419efb2fe8a9fe420f23be4846d187d0a8911bfa81cf831e62837a826ae0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96a17ebd05b28abfe9a16eb8f73e1f5f238c19eb15e1f68e1810362349e18eb3 0.600000000000 1475746 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": 1013045, "vin": [ { "gen": { "height": 1013035 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96a17ebd05b28abfe9a16eb8f73e1f5f238c19eb15e1f68e1810362349e18eb3" } } ], "extra": [ 1, 119, 70, 20, 25, 239, 178, 254, 138, 159, 228, 32, 242, 59, 228, 132, 109, 24, 125, 10, 137, 17, 191, 168, 28, 248, 49, 230, 40, 55, 168, 38, 174, 2, 17, 0, 0, 0, 4, 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