Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4d1920db2205df3ae3fcdd333fd20c60379e0c431fb021be4183f4f15cdd250

Tx prefix hash: dd56c49d5855725f13b25f23278e1a047bda753e09bbde04dfa4f23494003d0d
Tx public key: 42286b94af4afe9ae2125cd1645dff6262b4f5ee7ef68b84c5f40e759fe5a64f
Timestamp: 1698141280 Timestamp [UCT]: 2023-10-24 09:54:40 Age [y:d:h:m:s]: 01:159:10:02:58
Block: 876541 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374945 RingCT/type: yes/0
Extra: 0142286b94af4afe9ae2125cd1645dff6262b4f5ee7ef68b84c5f40e759fe5a64f02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.764990101000 dcy

stealth address amount amount idx
00: 023c4d7ba50e2f9ccf88b7348a0d7916a3b966029c5966e2f82a31b337f8d782 0.764990101000 1331871 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": 876551, "vin": [ { "gen": { "height": 876541 } } ], "vout": [ { "amount": 764990101, "target": { "key": "023c4d7ba50e2f9ccf88b7348a0d7916a3b966029c5966e2f82a31b337f8d782" } } ], "extra": [ 1, 66, 40, 107, 148, 175, 74, 254, 154, 226, 18, 92, 209, 100, 93, 255, 98, 98, 180, 245, 238, 126, 246, 139, 132, 197, 244, 14, 117, 159, 229, 166, 79, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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