Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10f0b241307a640b566b5ac2e12c7e9236d032f75c57a4efd522a413783f4307

Tx prefix hash: 4f5ac9fc5d56745ef71ea259d6e552957811586e52405a02eae293e848691905
Tx public key: a8621ad5d69182e57fd47556b22d00352742b82ecc4190ef572fd3cbd793572e
Timestamp: 1732117023 Timestamp [UCT]: 2024-11-20 15:37:03 Age [y:d:h:m:s]: 00:140:01:01:50
Block: 1157912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99909 RingCT/type: yes/0
Extra: 01a8621ad5d69182e57fd47556b22d00352742b82ecc4190ef572fd3cbd793572e0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a3da5dfa152e84e6fcdfc029dc465edae1fd0b90d2b5a939c5eed7fbc39b9c2 0.600000000000 1643535 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": 1157922, "vin": [ { "gen": { "height": 1157912 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a3da5dfa152e84e6fcdfc029dc465edae1fd0b90d2b5a939c5eed7fbc39b9c2" } } ], "extra": [ 1, 168, 98, 26, 213, 214, 145, 130, 229, 127, 212, 117, 86, 178, 45, 0, 53, 39, 66, 184, 46, 204, 65, 144, 239, 87, 47, 211, 203, 215, 147, 87, 46, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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