Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 825ff9a20f738ed6461b4d9904d4293382a5562c0a23a4bcd70dad5a5671b2ef

Tx prefix hash: 703d96544d915026328a287e160bb6a9966c19dd18e6bb1ffffd4444704c82a8
Tx public key: a638c9b6b4ba58e414d01cbfcd22e2205e70f56c4b570e28eb9f1a3a8c56b12a
Timestamp: 1706547419 Timestamp [UCT]: 2024-01-29 16:56:59 Age [y:d:h:m:s]: 01:295:00:04:44
Block: 946010 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 469648 RingCT/type: yes/0
Extra: 01a638c9b6b4ba58e414d01cbfcd22e2205e70f56c4b570e28eb9f1a3a8c56b12a02110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d71ebc95271ae6e0beb0fe374bcf8f905e12242a7584339b55d87404aa31419a 0.600000000000 1404340 of 15

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": 946020, "vin": [ { "gen": { "height": 946010 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d71ebc95271ae6e0beb0fe374bcf8f905e12242a7584339b55d87404aa31419a" } } ], "extra": [ 1, 166, 56, 201, 182, 180, 186, 88, 228, 20, 208, 28, 191, 205, 34, 226, 32, 94, 112, 245, 108, 75, 87, 14, 40, 235, 159, 26, 58, 140, 86, 177, 42, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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