Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7385e20173b651eed77b916db46dff0df1155c91eadce31bcda4e5ad9b710723

Tx prefix hash: 081c1947f621977059fde9c95e81a1291ba831cd7c14427c858781c53462e8c0
Tx public key: 8961100f214d45dbe4f4c7a2310dc5f7127b0d0c6c37dc7c11535841b7395a58
Timestamp: 1728737104 Timestamp [UCT]: 2024-10-12 12:45:04 Age [y:d:h:m:s]: 00:004:10:46:19
Block: 1129993 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3185 RingCT/type: yes/0
Extra: 018961100f214d45dbe4f4c7a2310dc5f7127b0d0c6c37dc7c11535841b7395a58021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b15adf029a761a8149854b8330c741bf3f3e433bb8ba50e9ed8a9e6b86029727 0.600000000000 1612864 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": 1130003, "vin": [ { "gen": { "height": 1129993 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b15adf029a761a8149854b8330c741bf3f3e433bb8ba50e9ed8a9e6b86029727" } } ], "extra": [ 1, 137, 97, 16, 15, 33, 77, 69, 219, 228, 244, 199, 162, 49, 13, 197, 247, 18, 123, 13, 12, 108, 55, 220, 124, 17, 83, 88, 65, 183, 57, 90, 88, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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