Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f8221c3258242c78c589388e7a6c820d5730266851a2f4e706dcbade92100ef

Tx prefix hash: fd3677a9cd80c7d217d453a72f6fcee6e50099ac3dd677fdef4239d82145e7ea
Tx public key: 074c76987a321035a28b2caf45976744bd1c5480dfb639639978e1590f4cad92
Timestamp: 1696432527 Timestamp [UCT]: 2023-10-04 15:15:27 Age [y:d:h:m:s]: 01:173:08:15:40
Block: 862372 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384916 RingCT/type: yes/0
Extra: 01074c76987a321035a28b2caf45976744bd1c5480dfb639639978e1590f4cad9202110000000be6d27f9c000000000000000000

1 output(s) for total of 0.852321836000 dcy

stealth address amount amount idx
00: 32d70fde76cbb9e09b0c8caa256f0c0dab7ee1bfe01a5d859611e33bcc120afc 0.852321836000 1316790 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": 862382, "vin": [ { "gen": { "height": 862372 } } ], "vout": [ { "amount": 852321836, "target": { "key": "32d70fde76cbb9e09b0c8caa256f0c0dab7ee1bfe01a5d859611e33bcc120afc" } } ], "extra": [ 1, 7, 76, 118, 152, 122, 50, 16, 53, 162, 139, 44, 175, 69, 151, 103, 68, 189, 28, 84, 128, 223, 182, 57, 99, 153, 120, 225, 89, 15, 76, 173, 146, 2, 17, 0, 0, 0, 11, 230, 210, 127, 156, 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