Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcc7a0d2f4de965d5768bb159774c9b4d4ae3995fd83226d2a890ffb30f2efed

Tx prefix hash: 020ff05c4f5e3441f70de45774dfb6a23b3460924d03c6728438e9dd40791d33
Tx public key: f9f2456411afc6b3decc1f8913bc9793da836ebac19ab9ecb543ea64c9c00bff
Timestamp: 1707222977 Timestamp [UCT]: 2024-02-06 12:36:17 Age [y:d:h:m:s]: 01:061:22:28:28
Block: 951612 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305318 RingCT/type: yes/0
Extra: 01f9f2456411afc6b3decc1f8913bc9793da836ebac19ab9ecb543ea64c9c00bff02110000000210a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76c333d23f05c3f5f2ab89727ed591c62f81ca4cc2f41a22ea58a7d5f68b60ff 0.600000000000 1410400 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": 951622, "vin": [ { "gen": { "height": 951612 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76c333d23f05c3f5f2ab89727ed591c62f81ca4cc2f41a22ea58a7d5f68b60ff" } } ], "extra": [ 1, 249, 242, 69, 100, 17, 175, 198, 179, 222, 204, 31, 137, 19, 188, 151, 147, 218, 131, 110, 186, 193, 154, 185, 236, 181, 67, 234, 100, 201, 192, 11, 255, 2, 17, 0, 0, 0, 2, 16, 161, 116, 143, 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