Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38b07439835fd7c9bb3b4305bc13c3d1316c6385f8437658dadafe3969d7c6e5

Tx prefix hash: 1484eb6e380b6872950bfa9b643e5c39716290a690395e631f40ed7ee3cc9dcd
Tx public key: 3c26395c1289a70cb090c48a0d6f0640a0eb95bc70a622199f11d92366e72954
Timestamp: 1695598269 Timestamp [UCT]: 2023-09-24 23:31:09 Age [y:d:h:m:s]: 01:125:06:50:15
Block: 855450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350603 RingCT/type: yes/0
Extra: 013c26395c1289a70cb090c48a0d6f0640a0eb95bc70a622199f11d92366e729540211000000054b8f5122000000000000000000

1 output(s) for total of 0.898543454000 dcy

stealth address amount amount idx
00: 16d267d3214dfe2be5b8c66f662a1c5dd5d646adc9d6dbe34387f89ea46ee508 0.898543454000 1309472 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": 855460, "vin": [ { "gen": { "height": 855450 } } ], "vout": [ { "amount": 898543454, "target": { "key": "16d267d3214dfe2be5b8c66f662a1c5dd5d646adc9d6dbe34387f89ea46ee508" } } ], "extra": [ 1, 60, 38, 57, 92, 18, 137, 167, 12, 176, 144, 196, 138, 13, 111, 6, 64, 160, 235, 149, 188, 112, 166, 34, 25, 159, 17, 217, 35, 102, 231, 41, 84, 2, 17, 0, 0, 0, 5, 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