Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f4d39fe96e63dc973636ec56f7f422a87ef88b32c7f10f18e3411a1e368297f

Tx prefix hash: b7a11bdc566b2066ab3ad10b32a1d75c03b2106d6e06f0f1b605ae78c91310cf
Tx public key: d34758f782ac8bbaf8f87b180bbc0a54e83a9e7065e3f0e25ab4d68ff5fb2bd3
Timestamp: 1677324531 Timestamp [UCT]: 2023-02-25 11:28:51 Age [y:d:h:m:s]: 02:044:17:07:34
Block: 704634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 553544 RingCT/type: yes/0
Extra: 01d34758f782ac8bbaf8f87b180bbc0a54e83a9e7065e3f0e25ab4d68ff5fb2bd302110000000274b6d784000000000000000000

1 output(s) for total of 2.839585547000 dcy

stealth address amount amount idx
00: 719020229e42a04796617f60b9a2b12de28b4d2cfdb62b017ee1e194908a15bc 2.839585547000 1148305 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": 704644, "vin": [ { "gen": { "height": 704634 } } ], "vout": [ { "amount": 2839585547, "target": { "key": "719020229e42a04796617f60b9a2b12de28b4d2cfdb62b017ee1e194908a15bc" } } ], "extra": [ 1, 211, 71, 88, 247, 130, 172, 139, 186, 248, 248, 123, 24, 11, 188, 10, 84, 232, 58, 158, 112, 101, 227, 240, 226, 90, 180, 214, 143, 245, 251, 43, 211, 2, 17, 0, 0, 0, 2, 116, 182, 215, 132, 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