Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 842e827af166a2e3445e099ad2cc6fc52bda4223ce8b0fbc46012908f8c3b0ff

Tx prefix hash: f49230aeeb4bf51d44d0051d26dd2451ab986c7c75749aac8bf7dcec08dfc18b
Tx public key: c33ae2551d25b72cdf44a82d47d9958a714b54f7c59f3dfdf9ee3fb463f3794a
Timestamp: 1577701800 Timestamp [UCT]: 2019-12-30 10:30:00 Age [y:d:h:m:s]: 05:065:18:16:13
Block: 34943 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1196772 RingCT/type: yes/0
Extra: 01c33ae2551d25b72cdf44a82d47d9958a714b54f7c59f3dfdf9ee3fb463f3794a021100000003d81c26c0000000000000000000

1 output(s) for total of 470.132408797000 dcy

stealth address amount amount idx
00: a5cb8103dcc08cbbc2ee2f64e9a663d08235207cf8d7221e7ddd1907a997433a 470.132408797000 58860 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": 34953, "vin": [ { "gen": { "height": 34943 } } ], "vout": [ { "amount": 470132408797, "target": { "key": "a5cb8103dcc08cbbc2ee2f64e9a663d08235207cf8d7221e7ddd1907a997433a" } } ], "extra": [ 1, 195, 58, 226, 85, 29, 37, 183, 44, 223, 68, 168, 45, 71, 217, 149, 138, 113, 75, 84, 247, 197, 159, 61, 253, 249, 238, 63, 180, 99, 243, 121, 74, 2, 17, 0, 0, 0, 3, 216, 28, 38, 192, 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