Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 739ab0e824730d3bb9a864abbbc019ea54d99cc51bc483517d0739447472fbdf

Tx prefix hash: 81c842d2908591092e18654b5619423d5df64fbd27c0667401c950b4eea43932
Tx public key: 769698186af6c26e0cfaadc5d6247336a09e9b0bf1d947b635c0af1ac2f7c10d
Timestamp: 1706285331 Timestamp [UCT]: 2024-01-26 16:08:51 Age [y:d:h:m:s]: 01:029:18:55:04
Block: 943831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282345 RingCT/type: yes/0
Extra: 01769698186af6c26e0cfaadc5d6247336a09e9b0bf1d947b635c0af1ac2f7c10d02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f417bd4a465ae0f046ee771b28d97bd30ddd112afb5e5a9ba9d713bb1b418cfa 0.600000000000 1402057 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": 943841, "vin": [ { "gen": { "height": 943831 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f417bd4a465ae0f046ee771b28d97bd30ddd112afb5e5a9ba9d713bb1b418cfa" } } ], "extra": [ 1, 118, 150, 152, 24, 106, 246, 194, 110, 12, 250, 173, 197, 214, 36, 115, 54, 160, 158, 155, 11, 241, 217, 71, 182, 53, 192, 175, 26, 194, 247, 193, 13, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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