Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b356ce2301560604164e03790cce513dc6053d8ef914e049370420a1c8f36e06

Tx prefix hash: bdf1c9645779da8bb9e27cbacf06d9a5647865815c540f908eb2d90f6c90eff0
Tx public key: 05be3151a0739e68a172a482e02d5a665df28317a2d59d8dd2037b2a47fa43e7
Timestamp: 1672974471 Timestamp [UCT]: 2023-01-06 03:07:51 Age [y:d:h:m:s]: 02:009:20:28:01
Block: 668556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 528939 RingCT/type: yes/0
Extra: 0105be3151a0739e68a172a482e02d5a665df28317a2d59d8dd2037b2a47fa43e702110000000752542ceb000000000000000000

1 output(s) for total of 3.739352444000 dcy

stealth address amount amount idx
00: 0d816f9430510596967c0d3ca507d3b68a6c767a6ae400176a8387d26fff8e58 3.739352444000 1109807 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": 668566, "vin": [ { "gen": { "height": 668556 } } ], "vout": [ { "amount": 3739352444, "target": { "key": "0d816f9430510596967c0d3ca507d3b68a6c767a6ae400176a8387d26fff8e58" } } ], "extra": [ 1, 5, 190, 49, 81, 160, 115, 158, 104, 161, 114, 164, 130, 224, 45, 90, 102, 93, 242, 131, 23, 162, 213, 157, 141, 210, 3, 123, 42, 71, 250, 67, 231, 2, 17, 0, 0, 0, 7, 82, 84, 44, 235, 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