Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ed1cc40c68da8c63abc7f35b9102941f531353c91a4839ec76ffee8e078fe4d

Tx prefix hash: 3be1ea4f2de63fa5c1b2c203222aee138b147caa8bfdd54f1362e6cee5f42241
Tx public key: 51ba3fd3a8cdea17e90bbfc5ec24b12580867e0cdf6f486f74b5499c14b99774
Timestamp: 1578328619 Timestamp [UCT]: 2020-01-06 16:36:59 Age [y:d:h:m:s]: 05:125:14:26:15
Block: 39825 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1239887 RingCT/type: yes/0
Extra: 0151ba3fd3a8cdea17e90bbfc5ec24b12580867e0cdf6f486f74b5499c14b9977402110000003bdcee4b4d000000000000000000

1 output(s) for total of 452.943561620000 dcy

stealth address amount amount idx
00: 1207c8d2c76c9aa05436acf56df0ca666c6b735d7b6c3ccabd1c0777c238f46a 452.943561620000 69217 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": 39835, "vin": [ { "gen": { "height": 39825 } } ], "vout": [ { "amount": 452943561620, "target": { "key": "1207c8d2c76c9aa05436acf56df0ca666c6b735d7b6c3ccabd1c0777c238f46a" } } ], "extra": [ 1, 81, 186, 63, 211, 168, 205, 234, 23, 233, 11, 191, 197, 236, 36, 177, 37, 128, 134, 126, 12, 223, 111, 72, 111, 116, 181, 73, 156, 20, 185, 151, 116, 2, 17, 0, 0, 0, 59, 220, 238, 75, 77, 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