Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: adf51d841971cf1f7b10d8d41481243c5636a3f3eed37182aaee9252a2166678

Tx prefix hash: 8e44e3f031cc628faca0cc769ba20f2755e9faa6877a3469a4ae441ea56221f3
Tx public key: 0a7585ee400dfbecd15fc0d766b34dc3cd8ae65d89c7c714fb0e5afcb7b38c0a
Timestamp: 1656941255 Timestamp [UCT]: 2022-07-04 13:27:35 Age [y:d:h:m:s]: 02:225:00:26:56
Block: 536495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 681919 RingCT/type: yes/0
Extra: 010a7585ee400dfbecd15fc0d766b34dc3cd8ae65d89c7c714fb0e5afcb7b38c0a02110000000e2e6b1fd5000000000000000000

1 output(s) for total of 10.241640032000 dcy

stealth address amount amount idx
00: 44cc2ed4f962986100dbcd80df1f95dff28e1d7687917b4b1e134fd9e260db5e 10.241640032000 966264 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": 536505, "vin": [ { "gen": { "height": 536495 } } ], "vout": [ { "amount": 10241640032, "target": { "key": "44cc2ed4f962986100dbcd80df1f95dff28e1d7687917b4b1e134fd9e260db5e" } } ], "extra": [ 1, 10, 117, 133, 238, 64, 13, 251, 236, 209, 95, 192, 215, 102, 179, 77, 195, 205, 138, 230, 93, 137, 199, 199, 20, 251, 14, 90, 252, 183, 179, 140, 10, 2, 17, 0, 0, 0, 14, 46, 107, 31, 213, 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