Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3782a3055a06341cc0ef5978db96888adf5316e4ff8565f9a4a1d82177e555c6

Tx prefix hash: 1f2783682f66d30dbabc827fa05ed6930460dfce1e1472e5d9422728cdb1c905
Tx public key: f3362c74a2a6559fbd2a9430d3fa606c8a477d0233f40a73dcf5c8f469c6e5cc
Timestamp: 1707072655 Timestamp [UCT]: 2024-02-04 18:50:55 Age [y:d:h:m:s]: 00:353:04:11:40
Block: 950368 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252797 RingCT/type: yes/0
Extra: 01f3362c74a2a6559fbd2a9430d3fa606c8a477d0233f40a73dcf5c8f469c6e5cc02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8e0cad96869ca6a7df516cb63e9235a18fe62a901422446dff78239dfa1f5e4 0.600000000000 1408974 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": 950378, "vin": [ { "gen": { "height": 950368 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8e0cad96869ca6a7df516cb63e9235a18fe62a901422446dff78239dfa1f5e4" } } ], "extra": [ 1, 243, 54, 44, 116, 162, 166, 85, 159, 189, 42, 148, 48, 211, 250, 96, 108, 138, 71, 125, 2, 51, 244, 10, 115, 220, 245, 200, 244, 105, 198, 229, 204, 2, 17, 0, 0, 0, 2, 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