Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 854b8176dca3ab99bd9e45c5d803a00239f476c04e18c27c555b64bf187adfaf

Tx prefix hash: 8ad04eb0e2b1d07ccb5eaeae192e5a0b1630ae1c951988d58c7a1e6a1398081d
Tx public key: 1f7a51e21515e80d34c2285ad6d3506c40b7c33f33bbd50f93ced203f0a203df
Timestamp: 1723570941 Timestamp [UCT]: 2024-08-13 17:42:21 Age [y:d:h:m:s]: 00:301:04:59:04
Block: 1087164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215194 RingCT/type: yes/0
Extra: 011f7a51e21515e80d34c2285ad6d3506c40b7c33f33bbd50f93ced203f0a203df02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49c16b45e19e064a8e6b81179176a639ac2ddd0a5f1e6390a821ae0faa9a8da8 0.600000000000 1561769 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": 1087174, "vin": [ { "gen": { "height": 1087164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49c16b45e19e064a8e6b81179176a639ac2ddd0a5f1e6390a821ae0faa9a8da8" } } ], "extra": [ 1, 31, 122, 81, 226, 21, 21, 232, 13, 52, 194, 40, 90, 214, 211, 80, 108, 64, 183, 195, 63, 51, 187, 213, 15, 147, 206, 210, 3, 240, 162, 3, 223, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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