Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a2fb8dfcf459ff132ddb92521c531b5c88ef529430ecd4626375f1a3a0c8c58

Tx prefix hash: 970b4cfcf512784dd9af4f76d2bc23734213413e8a3cda8ccfcdbb774ab8bbb7
Tx public key: 4edd2d10e237e711ef660c8b74b98c115eb00afefc9c0ca7d5cfa5fa14e99841
Timestamp: 1709844323 Timestamp [UCT]: 2024-03-07 20:45:23 Age [y:d:h:m:s]: 01:058:02:18:55
Block: 973367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302532 RingCT/type: yes/0
Extra: 014edd2d10e237e711ef660c8b74b98c115eb00afefc9c0ca7d5cfa5fa14e9984102110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7990268190351420bb1a62aa495de0b3fc1d023d9ee7ecb163595ca0b6727c21 0.600000000000 1433302 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": 973377, "vin": [ { "gen": { "height": 973367 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7990268190351420bb1a62aa495de0b3fc1d023d9ee7ecb163595ca0b6727c21" } } ], "extra": [ 1, 78, 221, 45, 16, 226, 55, 231, 17, 239, 102, 12, 139, 116, 185, 140, 17, 94, 176, 10, 254, 252, 156, 12, 167, 213, 207, 165, 250, 20, 233, 152, 65, 2, 17, 0, 0, 0, 1, 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