Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b7962e57542099deac3b42ea8784bbbe2a84b7eefd5fa630193ec3072a1af56

Tx prefix hash: 0dff7b5636de8bc7de4faf89ab39f2d4cca544d966c6565c19ab30b74073547a
Tx public key: aa63ec12bad290113de9f8a3afc1896ac9cfe0c36e382f3aae8414f4a80873e5
Timestamp: 1700800567 Timestamp [UCT]: 2023-11-24 04:36:07 Age [y:d:h:m:s]: 01:057:09:26:42
Block: 898377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302374 RingCT/type: yes/0
Extra: 01aa63ec12bad290113de9f8a3afc1896ac9cfe0c36e382f3aae8414f4a80873e50211000000024b8f5122000000000000000000

1 output(s) for total of 0.647595841000 dcy

stealth address amount amount idx
00: c51655dfed062ea1602574abd4dcbf6098713fd62197f380bae461488e17a0d5 0.647595841000 1354790 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": 898387, "vin": [ { "gen": { "height": 898377 } } ], "vout": [ { "amount": 647595841, "target": { "key": "c51655dfed062ea1602574abd4dcbf6098713fd62197f380bae461488e17a0d5" } } ], "extra": [ 1, 170, 99, 236, 18, 186, 210, 144, 17, 61, 233, 248, 163, 175, 193, 137, 106, 201, 207, 224, 195, 110, 56, 47, 58, 174, 132, 20, 244, 168, 8, 115, 229, 2, 17, 0, 0, 0, 2, 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