Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24b776800030f0f88ec0e78a8923aad0bf7f9d61be07b2e1160a8e1e2c3e193c

Tx prefix hash: f4fa004e84a79a8de083f30bdc8afc9c27a7313f6e2be57bf53413218a87e9b1
Tx public key: ca159b043a41c37c73dab5bcf1b3a65dac412c39a4b815aeedab72d45c26fc2e
Timestamp: 1695440856 Timestamp [UCT]: 2023-09-23 03:47:36 Age [y:d:h:m:s]: 01:109:09:13:44
Block: 854140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339472 RingCT/type: yes/0
Extra: 01ca159b043a41c37c73dab5bcf1b3a65dac412c39a4b815aeedab72d45c26fc2e02110000000b75e3f0e9000000000000000000

1 output(s) for total of 0.907569015000 dcy

stealth address amount amount idx
00: fbd1238d8372c76fcf804842c6b63cf27b1cce4f28de102be6c8db68a4baa5d6 0.907569015000 1308096 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": 854150, "vin": [ { "gen": { "height": 854140 } } ], "vout": [ { "amount": 907569015, "target": { "key": "fbd1238d8372c76fcf804842c6b63cf27b1cce4f28de102be6c8db68a4baa5d6" } } ], "extra": [ 1, 202, 21, 155, 4, 58, 65, 195, 124, 115, 218, 181, 188, 241, 179, 166, 93, 172, 65, 44, 57, 164, 184, 21, 174, 237, 171, 114, 212, 92, 38, 252, 46, 2, 17, 0, 0, 0, 11, 117, 227, 240, 233, 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