Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8cd9c70ccfc0f60a25ef8f67735d86a75502e24e146257c999fee3c064db8aee

Tx prefix hash: d6f7eb4bb0b9ff674fe45c25a324e0209489c25bb37aebeac4bbdd7b75023147
Tx public key: 2577a01fa8d771dd8d36e37af1d0b1663349164d1a879f2909f449ce5be4e845
Timestamp: 1699261206 Timestamp [UCT]: 2023-11-06 09:00:06 Age [y:d:h:m:s]: 01:178:07:09:31
Block: 885622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388636 RingCT/type: yes/0
Extra: 012577a01fa8d771dd8d36e37af1d0b1663349164d1a879f2909f449ce5be4e845021100000003faf35c9c000000000000000000

1 output(s) for total of 0.713783787000 dcy

stealth address amount amount idx
00: 5ddc758e9c349316a9f903532f254cfebc49db0c3a744a645d90890e83e0a7da 0.713783787000 1341403 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": 885632, "vin": [ { "gen": { "height": 885622 } } ], "vout": [ { "amount": 713783787, "target": { "key": "5ddc758e9c349316a9f903532f254cfebc49db0c3a744a645d90890e83e0a7da" } } ], "extra": [ 1, 37, 119, 160, 31, 168, 215, 113, 221, 141, 54, 227, 122, 241, 208, 177, 102, 51, 73, 22, 77, 26, 135, 159, 41, 9, 244, 73, 206, 91, 228, 232, 69, 2, 17, 0, 0, 0, 3, 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