Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76d97032b4ac26142aed1e90c1f5eb3ad606d3d2d50006d7b720174ca0a6c0dc

Tx prefix hash: cd627a578b72aee26869534581ce8651a9d385003eb6b68bf0fc0003b6413b6b
Tx public key: d9910b1c9c9360d2b1d41c6144bd3323776b989810a6a918e879b453ab79871b
Timestamp: 1725015421 Timestamp [UCT]: 2024-08-30 10:57:01 Age [y:d:h:m:s]: 01:112:13:23:24
Block: 1099136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338944 RingCT/type: yes/0
Extra: 01d9910b1c9c9360d2b1d41c6144bd3323776b989810a6a918e879b453ab79871b02110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7d7f26f0c879a17268f3516eccc0031a166ef063e6d4b8b4d827568515c81a6 0.600000000000 1575063 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": 1099146, "vin": [ { "gen": { "height": 1099136 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7d7f26f0c879a17268f3516eccc0031a166ef063e6d4b8b4d827568515c81a6" } } ], "extra": [ 1, 217, 145, 11, 28, 156, 147, 96, 210, 177, 212, 28, 97, 68, 189, 51, 35, 119, 107, 152, 152, 16, 166, 169, 24, 232, 121, 180, 83, 171, 121, 135, 27, 2, 17, 0, 0, 0, 9, 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