Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d19c70f49dfc64ee55df002f6fade3e0839017ee889202f3e90587c4451d4f7

Tx prefix hash: d5fb72b524e5418b36311d25bc88f4a9307866c0a2381661f1b797d063e86aa3
Tx public key: 76afba739df9aff4f7adf2ce8363d90925cc0e75703db5dcfdabb078294a7c13
Timestamp: 1675623389 Timestamp [UCT]: 2023-02-05 18:56:29 Age [y:d:h:m:s]: 02:070:01:58:58
Block: 690537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 571708 RingCT/type: yes/0
Extra: 0176afba739df9aff4f7adf2ce8363d90925cc0e75703db5dcfdabb078294a7c13021100000001faf35c9c000000000000000000

1 output(s) for total of 3.162016928000 dcy

stealth address amount amount idx
00: adaa1fb9a1f0867f6bd4f6926a5b043135e45da257e2b28e7aadbf2f26595710 3.162016928000 1133267 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": 690547, "vin": [ { "gen": { "height": 690537 } } ], "vout": [ { "amount": 3162016928, "target": { "key": "adaa1fb9a1f0867f6bd4f6926a5b043135e45da257e2b28e7aadbf2f26595710" } } ], "extra": [ 1, 118, 175, 186, 115, 157, 249, 175, 244, 247, 173, 242, 206, 131, 99, 217, 9, 37, 204, 14, 117, 112, 61, 181, 220, 253, 171, 176, 120, 41, 74, 124, 19, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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