Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3a8b5e774e2c1e89ba23b19d4c8c264e8dd6c6dfa5c6b4d04dc84a69dac0936

Tx prefix hash: be79a9d36636e97604023e987d8bdee34cc7a21c840c2e1923cebbcda6c79370
Tx public key: 5a594b00436995abf07f34ee8466da7e61ee6447f49ef707ffa1282f175af94f
Timestamp: 1632481469 Timestamp [UCT]: 2021-09-24 11:04:29 Age [y:d:h:m:s]: 03:214:17:13:53
Block: 339955 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 929656 RingCT/type: yes/0
Extra: 015a594b00436995abf07f34ee8466da7e61ee6447f49ef707ffa1282f175af94f021100000008a272b9cb000000000000000000

1 output(s) for total of 45.877901173000 dcy

stealth address amount amount idx
00: fcded40219bbbcc3d58c95871a55e6a4d401d02ee15050259e60a46d771da7c1 45.877901173000 698942 of 0

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": 339965, "vin": [ { "gen": { "height": 339955 } } ], "vout": [ { "amount": 45877901173, "target": { "key": "fcded40219bbbcc3d58c95871a55e6a4d401d02ee15050259e60a46d771da7c1" } } ], "extra": [ 1, 90, 89, 75, 0, 67, 105, 149, 171, 240, 127, 52, 238, 132, 102, 218, 126, 97, 238, 100, 71, 244, 158, 247, 7, 255, 161, 40, 47, 23, 90, 249, 79, 2, 17, 0, 0, 0, 8, 162, 114, 185, 203, 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