Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b342d741623f618bb0ef3b97ee85b05ddb62f8665c6ab7d3cb891192034dc3c0

Tx prefix hash: fe2680f62b8556f48a0d1e904f65e66056cd59b658dc61990a7f8824843d518d
Tx public key: c6b626cfda60a8ec7216418e651d83ddde19b947ab8eab4cac63aa742a572ac3
Timestamp: 1696073190 Timestamp [UCT]: 2023-09-30 11:26:30 Age [y:d:h:m:s]: 01:217:18:54:17
Block: 859397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416714 RingCT/type: yes/0
Extra: 01c6b626cfda60a8ec7216418e651d83ddde19b947ab8eab4cac63aa742a572ac30211000000014b8f5122000000000000000000

1 output(s) for total of 0.871918660000 dcy

stealth address amount amount idx
00: 3543929193b35db3cc8a9847c23e578d8bb7ba428c2b109c82d8c44367d41a8a 0.871918660000 1313621 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": 859407, "vin": [ { "gen": { "height": 859397 } } ], "vout": [ { "amount": 871918660, "target": { "key": "3543929193b35db3cc8a9847c23e578d8bb7ba428c2b109c82d8c44367d41a8a" } } ], "extra": [ 1, 198, 182, 38, 207, 218, 96, 168, 236, 114, 22, 65, 142, 101, 29, 131, 221, 222, 25, 185, 71, 171, 142, 171, 76, 172, 99, 170, 116, 42, 87, 42, 195, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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