Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1233635573a6d95a7f1c63707e64e9fe3b342dbf9142cd619a761848d8093757

Tx prefix hash: ceb8b819e8adc786007b4d59d0b7dd35c52613ace9194beab09541ea41962b6e
Tx public key: 8f86bc3fcaa1f250c9a2d83ca60c3605d9b2277023c769ec9b897cbeadbed376
Timestamp: 1686327968 Timestamp [UCT]: 2023-06-09 16:26:08 Age [y:d:h:m:s]: 01:334:15:00:35
Block: 778655 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 500350 RingCT/type: yes/0
Extra: 018f86bc3fcaa1f250c9a2d83ca60c3605d9b2277023c769ec9b897cbeadbed3760211000000014b8f5122000000000000000000

1 output(s) for total of 1.614332206000 dcy

stealth address amount amount idx
00: 2dc64fee3a5e11e81bb516bc2c7da875bf791407d7743cfb48b5414249f54b99 1.614332206000 1228290 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": 778665, "vin": [ { "gen": { "height": 778655 } } ], "vout": [ { "amount": 1614332206, "target": { "key": "2dc64fee3a5e11e81bb516bc2c7da875bf791407d7743cfb48b5414249f54b99" } } ], "extra": [ 1, 143, 134, 188, 63, 202, 161, 242, 80, 201, 162, 216, 60, 166, 12, 54, 5, 217, 178, 39, 112, 35, 199, 105, 236, 155, 137, 124, 190, 173, 190, 211, 118, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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