Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a056d68bea86c1bf5e719c8df6828ad83b03a90a035628985eec70adcf5fa0ef

Tx prefix hash: 99a4097cb33cd07d0d2d3cb1f6122cd38fae4096cf38eea6bd210c49adfcd809
Tx public key: cc72b942daca0e40cb3a251919138fc2e36be6650eb4c282dd0df61003b1e3e6
Timestamp: 1708824363 Timestamp [UCT]: 2024-02-25 01:26:03 Age [y:d:h:m:s]: 00:322:09:26:23
Block: 964912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230783 RingCT/type: yes/0
Extra: 01cc72b942daca0e40cb3a251919138fc2e36be6650eb4c282dd0df61003b1e3e602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f44fee3178046ee5cdf7b28ed0b3deca82a9fc40a276008fcf7435a5683c7e1 0.600000000000 1424655 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": 964922, "vin": [ { "gen": { "height": 964912 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f44fee3178046ee5cdf7b28ed0b3deca82a9fc40a276008fcf7435a5683c7e1" } } ], "extra": [ 1, 204, 114, 185, 66, 218, 202, 14, 64, 203, 58, 37, 25, 25, 19, 143, 194, 227, 107, 230, 101, 14, 180, 194, 130, 221, 13, 246, 16, 3, 177, 227, 230, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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